This will require theforeman/foreman-packaging#11839 to work properly. But our "setup repos" scripts are Foreman version agnostic, and would also apply when building 3.19 and older.

Question: Do we want to backport the packaging change (should be safe, but… you know how things go) or introduce a if/else in the hook that sets up Puppet for 3.19 and older and OpenVox for 5.0+ (we did similar things for NodeJS in the past)?

Question: Do we want to backport the packaging change (should be safe, but… you know how things go) or introduce a if/else in the hook that sets up Puppet for 3.19 and older and OpenVox for 5.0+ (we did similar things for NodeJS in the past)?

I consider it an oversight for 3.19 so I'd be OK with backporting. Perhaps aim for consistency with RPM builds?

As we're still building 3.18.z, it would also need to go there to keep builds working.
But theforeman/foreman-packaging#12533 landed in 3.17, so you could say backporting that to 3.18 is also fair game.

OpenVox was backported to deb/3.18 and deb/3.19 are we ready to undraft this PR?

• deb/3.19: Backport: Add support for OpenVox agent foreman-packaging#13618
• deb/3.18: Backport: Add support for OpenVox agent foreman-packaging#13619

Ruby Rhod voice Super ready!